The objective is to do work on each requirement such that each requirement complies to a set of quality criteria. The exact quality criteria are established and described as part of the engagement in the Requirements Management Plan. The level of quality may be indicated by the SMART rule where each requirement should be:

S pecific

M easurable

A ttainable

R ealisable

T raceable or (T ime)

Note : There are a number of different interpretations for the SMART acronym.

As a minimum the following quality criteria are considered to be applicable:

• 1. completeness - each requirement should be in itself complete so that it can be read and understood as an independent requirement
• 2. clarity - given the context of the engagement and client environment each requirement should be understood by the involved business user or involved IT user without further clarification.
• 3. terminology - the terminology used in the requirement should be common business English or be clarified in the business glossary
• 4. references - each requirement should specify to what element(s) in the various models the business requirements applies. For instance a requirement stating that a specific level of security should be applied should also specify to which element(s) this applies in the As-Is and To-Be model like a business process or an application.
• 5. measurability - where possible numbers, values or ranges should be stated in each requirement to enable direct measurement of whether the requirement is